Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1583

reference: 336-tree-1
name: 1583
tree-preservation-order: undefined
336-tpo-1
uprn
address-text
point: POINT (-1.044470 50.894547)
geometry: MULTIPOLYGON (((-1.044413 50.894541,-1.044416 50.894552,-1.044424 50.894562,-1.044436 50.894570,-1.044452 50.894575,-1.044469 50.894577,-1.044487 50.894576,-1.044503 50.894571,-1.044516 50.894563,-1.044524 50.894553,-1.044527 50.894542,-1.044524 50.894531,-1.044516 50.894520,-1.044504 50.894512,-1.044488 50.894507,-1.044471 50.894505,-1.044453 50.894507,-1.044437 50.894512,-1.044424 50.894520,-1.044416 50.894530,-1.044413 50.894541)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL